home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_1
/
lcnt150u.zip
/
TEST.DOC
< prev
next >
Wrap
Text File
|
1991-12-19
|
4KB
|
88 lines
TEST.EXE - a utility to check whether FILES.BBS (or any file) has
been recently updated. (changed).
If a user uploads a file and enters a description then you should run
maintenance in your uploads directory. The next user will see your
Files.Bbs in perfect appearance. This is really necessary if you are
using the advanced colour options. The obvious solution is too run
maintenance after every user, but this method will only run Logcount
if it is really necessary.
Typeing TEST will produce this brief help screen.
┌──────────────────────────────────────────────────────────┐
│ Compare this .EXE's file Time/Date with another File. │
│ Reset .EXE's time to new time if other file updated. │
└──────────────────────────────────────────────────────────┘
Usage: EXE_filename <Filename> <TimeName> <Q>
<filename> is a fully qualified path to a file you want to
monitor. If this file is updated then this
EXE_filename will set it's own time to that new
time and will exit with errorlevel 10. If the
monitored file has not been updated then nothing
much happens, errorlevel 0 is returned. Batch
programs can check for these error conditions
and appropriate tasks can be performed.
<TimeName> is a fully qualified path to a file you want to
store the Updated file's Time/Date Stamp. Note,
this file's time/date stamp will be changed, not
the EXE_filename.
<Q> Run Quietly - very little is displayed to screen.
-----------------------------------------------------------------------
O.K. here's how this works.
Example 1. Checking Files.BBS in uploads directory
Test c:\f\uploads\files.bbs rem check if file updated
if errorlevel 10 logcount -cmaint.cfg rem do maint if required.
Test c:\f\uploads\Files.bbs rem reset time if Maintenance done.
Maint.Cfg
--------------
-LMaint.cfg % lets read this .cfg file. We won't find anything to count
-X< % but LOGCOUNT refuses to run if no LOGFILE is declared.
-Y> % picked -L (CBCS log) to avoid any extra MAILER functions
-M2 % put any non default options in here also.
-Tm % 'Truncate' for Maximus. - adjust 3 line descriptions.
-wc:\f\uploads % This the directory for maintenance.
Logcount will run, it will completely format the files.bbs to all options.
It will add any missing download indicators with blank entries. Etc...
This 'Maintenance' will accomplish the same thing as if a file had been
downloaded from the specified area. Test must be immediately run again
because maintenance will have been performed and the timestamp was altered.
Example 2.
Test c:\max\ul.log rem let's check Maximus' UPLOADS logfile.
if errorlevel 10 logcount -cmaint.cfg rem do maint if required.
There is no need to run TEST.EXE immediately since LOGCOUNT has not been
working on the target file. It and TEST will still have the same timestamp.
Both these example use the executing .EXE file to store the time/date stamp.
If you want to use TEST to keep track of many different files the use the
advanced option and store the time/date stamp on other non essential files.
Stuff like Yell.bbs, batch files, any file you aren't to concerned whether
it's date/time stamp gets altered. This tip is for other applications, but
if you use this program with only Logcount then using TEST.EXE to store the
date/time stamp is probably the best method.
P.S. Test.exe can be renamed any legal name. TEST.EXE knows where it is
(on the path, or in current director).
Note: Test.Exe probably will not work on Local Area Network Drives. I have
only tested it on an XT with a single Hardisk & 2 floppy diskettes.
RAFware November 14, 1990.